-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable LVM devices file when running image installs #5325
Disable LVM devices file when running image installs #5325
Conversation
This depends on storaged-project/blivet#1169 but strictly speaking isn't really blocked by it thanks to Python magic which allows setting non-existing attributes :-) |
/kickstart-test --testtype smoke |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thank you!
So, what's wrong with these tests? |
No idea:
|
96876c9
to
b6ae2e7
Compare
/kickstart-test --testtype smoke |
So rebasing to the latest master fixed the unit test and now packit is failing :-) |
@vojtechtrefny it fails with:
We no longer require anaconda-user-help so I guess it's some old version of the GUI pulled in here. Feel free to ignore till we resolve this. |
b6ae2e7
to
da09c0d
Compare
The new blivet flag allows us to control whether the LVM devices file will be populated with PVs or not and we don't want to write the file when running an image installation. Resolves: rhbz#2247872
da09c0d
to
ae2533c
Compare
/kickstart-test --testtype smoke |
Follow up for rhinstaller#5325 which disables the LVM devices file usage on blivet side but we also need to skip writing the file when writing the storage configuration post install. Resolves: rhbz#2247872
Follow up for rhinstaller#5325 which disables the LVM devices file usage on blivet side but we also need to skip writing the file when writing the storage configuration post install. Resolves: rhbz#2247872
Follow up for rhinstaller#5325 which disables the LVM devices file usage on blivet side but we also need to skip writing the file when writing the storage configuration post install. Resolves: rhbz#2247872
Follow up for rhinstaller#5325 which disables the LVM devices file usage on blivet side but we also need to skip writing the file when writing the storage configuration post install. Resolves: rhbz#2247872
Follow up for rhinstaller#5325 which disables the LVM devices file usage on blivet side but we also need to skip writing the file when writing the storage configuration post install. Resolves: rhbz#2247872
Follow up for rhinstaller#5325 which disables the LVM devices file usage on blivet side but we also need to skip writing the file when writing the storage configuration post install. Resolves: rhbz#2247872
The new blivet flag allows us to control whether the LVM devices file will be populated with PVs or not and we don't want to write the file when running an image installation.
Resolves: rhbz#2247872